-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8360562: sun/security/tools/keytool/i18n.java add an ability to add comment for failures #26412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Welcome back myankelevich! A progress list of the required criteria for merging this PR into |
|
@myankelev This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 1265 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
…dd comment for failures
|
@myankelev The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
|
@myankelev Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Webrevs
|
|
@myankelev This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a |
|
@myankelev This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
|
/open |
|
@myankelev This pull request is now open |
|
/open |
|
@myankelev This pull request is already open |
|
Is this enhancement requested related to some test failure that were not clear to triage? The fix looks good but is there a need for it? |
Yes, the error was missed several times before, as there was no comment. The error itself turned out to be a non-issue, but it was still missed and triaging it took quite a bit of time. This particular issue was documented here JDK-8360400. After evaluation the decision was made to remove the test case after JDK-8360416. |
|
/integrate |
|
Going to push as commit ebb6fd7.
Your commit was automatically rebased without conflicts. |
|
@myankelev Pushed as commit ebb6fd7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
When the test is run now the reason for the failure will be requested providing further feedback.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26412/head:pull/26412$ git checkout pull/26412Update a local copy of the PR:
$ git checkout pull/26412$ git pull https://git.openjdk.org/jdk.git pull/26412/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26412View PR using the GUI difftool:
$ git pr show -t 26412Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26412.diff
Using Webrev
Link to Webrev Comment